N4 supports EDIFACT standard COPRAR LOADLIST message, release D & version 95B.
This COPRAR LoadList Message (COPRAR D 95B) permits the transfer of data from a line operator to the terminal operator.
The line operator may send the following details to the terminal operator:
Outbound Vessel Visit Details
Container Details
Equipment Order Details
Hazard Details
Commodity Details
Reefer Requirements (CO2, O2, Humidity, and Ventilation requirements)
This specification provides the definition of the COPRAR D 95B Inbound LoadList message to be used in Electronic Data Interchange (EDI) between line operator and the marine terminal primarily to indicate which containers should be loaded to a vessel.
NOTE: You must use the COARRI Outbound Activity message (vessel-specific) message instead of the outbound COPRAR Loadlist EDI message for the Export/Transhipment units intended to be loaded onto the vessel later. Also, you must use the Carrier O/B Actual Visit Ref and Transit State fields in the Filter Criteria in the EDI Session form (on page 1) when you extract the COARRI Outbound Activity (Loadlist) EDI message. For more information, see Extract outbound EDI messages for the Export/Transhipment units (on page 1).
The following sections of this document explain how COPRAR D 95BLoadList message is handled in N4 and scope of its implementation. This message is basically used for the following purposes:
The line operator will send the outbound vessel visit details to the terminal operator.
The terminal operator will plan for the vessel visit that is send by the line operator.
The terminal operator will also plan for the containers received through the message.
COPRAR D 95B Inbound Supported Segments
Following table illustrates the segments of EDIFACT standard COPRAR D 95B message & scope of each segment in N4.
S. No |
Group |
Segment ID |
Supported Qualifier |
Description |
Supported in N4? |
---|---|---|---|---|---|
1 |
|
UNB |
|
Interchange Header (sender, receiver) |
Supported |
2 |
|
UNH |
|
Message Header (message type, message reference number) |
Supported |
3 |
|
BGM |
|
Beginning of message (message function) |
Supported |
4 |
|
FTX |
|
Free text |
Not Supported |
5 |
|
RFF |
XXX, ACW |
Reference |
Not Supported |
6 |
SG1 |
TDT |
|
Details Of Transport (O/B vessel details) |
Supported |
7 |
|
RFF |
|
Reference |
Not Supported |
8 |
|
LOC |
|
Place/Location Identification |
Not Supported |
9 |
|
DTM |
132, 133 |
Estimated Time Arrival/Departure of O/B vessel (132/133) |
Supported |
10 |
|
FTX |
|
Free text |
Not Supported |
11 |
SG2 |
NAD |
CA, CF, SLS |
Name And Address |
Not Supported |
12 |
|
CTA |
|
Contact Information |
Not Supported |
13 |
SG3 |
EQD |
CN |
Equipment Details |
Supported |
14 |
|
RFF |
BN, ABT |
Reference |
Supported |
15 |
|
EQN |
|
Number Of Units |
Not Supported |
16 |
|
TMD |
2, 3, 4, 5 |
Transport Movement Details |
Not Supported |
17 |
|
DTM |
|
Date/Time/Period |
Not Supported |
18 |
|
LOC |
7, 9, 11, PDS |
Place/Location Identification (delivery, destination, discharge) |
Supported |
19 |
|
MEA |
|
Measurement (gross weight) |
Supported |
20 |
|
DIM |
5, 6, 7, 8, 9 |
Dimensions (front, back, right, left, top) |
Supported |
21 |
|
TMP |
|
Temperature (preferred temperature) |
Supported |
22 |
|
RNG |
|
Range (Minimum, Maximum) |
Supported |
23 |
|
SEL |
CA, CU, QA, SH |
Seal Number (carrier, customs, quarantine, shipper) |
Supported |
24 |
|
FTX |
AAA, HAN |
Free Text (goods description, handling instructions |
Supported |
25 |
|
DGS |
|
Dangerous Goods |
Supported |
26 |
|
EQA |
CN, CH, RG |
Attached Equipment (payload unit, chassis, reefer generator) |
Supported |
27 |
SG4 |
TDT |
|
Details Of Transport (Inbound - truck/train/vessel details) |
Supported |
28 |
|
RFF |
|
Reference |
Not Supported |
29 |
|
LOC |
|
Place/Location Identification |
Not Supported |
30 |
|
DTM |
|
Date/Time/Period (Estimated Time Arrival of I/B Vessel Visit) |
Supported |
31 |
|
NAD |
|
Name And Address (Container Operator) |
Supported |
32 |
|
CNT |
|
Control Total |
Not Supported |
33 |
|
UNT |
|
Message Trailer |
Not Supported |
COPRAR Inbound - Message Functions
As per EDIFACT standard, COPRAR has various message function codes in BGM segment and N4 supports the following message functions are supported
BGM+661+WCP00000530901+3+AB' -- Here "3" is the message function qualifier
Qualifier in the EDI message |
Value in the XML |
---|---|
1 or 3 |
D - Delete |
Any Other Qualifier |
Default Behavior |
For information on the EDI message functions supported by COPRAR, see Supported EDI message functions (on page 1).
COPRAR D 95B Inbound N4 Built-in Map
N4 serves a built-in map which is used to convert COPRAR Edi message into Navis standard loadlist xml. This xml in turn used for further processing.
Following are the related files, part of N4 application and can be downloaded:
coprar(load)_D_95B.mgt- GoXml map
coprar.dic -Edifact standard dictionary
loadlist.xsd - Navis standard xml schema
Special Cases
edi:ediInboundVesselVisit
Added a filter (/EDI/Group_Loop/COPRAR/SG3/SG4/TDT/C220@A_8067=='1' || /EDI/Group_Loop/COPRAR/SG3/SG4/TDT/C220@A_8067=='8') such that it will be displayed only when the SG4 TDT has qualifer "1" (maritime transport) or "8"(inland water transport).
edi:ediTrainVisit
Added a filter (/EDI/Group_Loop/COPRAR/SG3/SG4/TDT/C220@A_8067=='2') such that it will be displayed only when the SG4 TDT has qualifier "2" (rail transport).
edi:ediTruck
Added a filter (/EDI/Group_Loop/COPRAR/SG3/SG4/TDT/C220@A_8067=='3') such that it will be displayed only when the SG4 TDT has qualifier "3" (road transport).
COPRAR D 95B Inbound Special Cases
Multi-facility scenario
If the given container in the EDI file is Active in other facility, the system will create a new advised unit for the given facility.
N4 has a way of validating some business conditions which might be applicable for some clients and not for some. So those validations are made configurable, the user may turn it on if the particular validation is needed or turn it off if not needed.
The following table lists such configurable settings applicable for COPRAR LoadList EDI message:
Name |
Description |
Edit UI |
Usage |
---|---|---|---|
ARGOLOADLIST001 |
List of Permissions to apply for Load List |
Session > Settings |
To apply all the selected permissions for the given containers in the COPRAR EDI message. |
ARGOLOADLIST002 |
Validate equipment type ISO |
Session > Settings |
Set it to true to validate the equipment type provided by the LOADLIST EDI message and generate an error if the equipment type is not found in the system. |
ARGOLOADLIST003 |
Parameter to convert container category from IMPORT to TRANSSHIP |
Session > Settings |
To change the container category from Import to Transship. |
UNB+UNOA:1+LAJPARTNER::SCAC+EUROGATECTW+130713:0851+150'
UNH+15000001+COPRAR:D:95B:UN'
BGM+121+20130713085107+9'
RFF+XXX:1'
TDT+20+001+1++APL:172:20+++L1234:103::LAJIT VESSEL'
LOC+9+NZLYT:139:6'
DTM+132:201307140600:203'
DTM+133:201307170600:203'
NAD+CF+APL:160:20'
EQD+CN+PRAP0202111+2200:102:5+++5'
RFF+BN:560099796'
DTM+WAT:201407031341:203'
LOC+11+SGSIN:139:6'
LOC+9+NZLYT:139:6'
MEA+AAE+VGM+KGM:21000'
SEL+22065+SH'
FTX+AAA+++LACTIC ACID FEED GRADE'
EQA+CN+PAY315398'
EQA+CN+PAY315399'
NAD+AM+APL'
EQD+CN+MSAU0202111+2200:102:5+++5'
RFF+BN:560099796'
DTM+WAT:201407031341:203'
LOC+11+SGSIN:139:6'
LOC+9+NZLYT:139:6'
MEA+AAE+VGM+KGM:21000'
SEL+22065+SH'
FTX+AAA+++LACTIC ACID FEED GRADE'
EQA+CN+PAL444555'
EQA+CN+PAL222333'
NAD+AM+APL'
CNT+1:1'
UNT+8005+15000001'
UNZ+1+150'
COPRAR D 95B Inbound Validations
Pre-Requisite to post a load list message:
Container Id, operator
Routing points must be in the itinerary
Vessel visit must be present else system tries to create Preliminary vessel visit if auto creation of vessel visit is enabled provided vessel info is given.
The line operator must be a shared line of the vessel visit if "SP_VALIDATE_LINE_PER_VSL" setting is enabled
ISO code must be valid if "LDL_VALIDATE_EQ_TYPE" is enabled